This is wrong, as the use statement is being removed. One of the new sniffs must be misbehaving. Edit: It's UseFromSameNamespace.

Looking at it, UseFromSameNamespace is actually correct because the use statement is in the global namespace, where it's not needed. Would still rather UseBeforeNamespace is triggered.

Can use a namespaced class to get round this for now.

(Just checked what happens and the code's going to be broken either way.)

good practice

for classes, this is expected

I can see this becoming annoying for many PHP functions e.g. all strlen and similar which gets used everywhere. Even Java auto-import java.lang to avoid too many imports. PHP provides the fallback too for functions (but not for classes IIRC).

If anything I would forbid defining a strlen that is not \strlen, which tries to avoid the ambiguity.

Some functions get a very-minor performance boost by not checking the fallback. But more importantly prevents https://www.giorgiosironi.com/2010/09/monkey-patching-in-php.html (as used by Symfony's ClockMock).

Might be annoying when not using an IDE though...

Let's try it out, we can always reverse it if needed.

(It's in use at https://github.com/doctrine/doctrine2/blob/b40c2c6b7893c929f754150d480c20f9b22e0afe/lib/Doctrine/ORM/Mapping/Factory/Strategy/FileWriterClassMetadataGeneratorStrategy.php#L9-L17 if you want to try your editor.)